This document provides some frequently asked questions about Sandra. Please read the Help File as well!
Q: I cannot install it on Windows NT/2000/XP - I get Can't run 16-bit Windows program. This application is not supported by Windows!
A: You will need to update some OS libraries, for more information see Microsoft KB Article.
Q: The Performance Tune-Up Wizard crashes!
A: The problem lies with another module. If only one module crashes, the wizard will not work since it runs all enabled modules. First find the module with the problem and fix it (see below). If you cannot fix it, delete the module (select it and press Del). The Wizard will skip the module.
Q: Sandra locks up at splash screen in Windows 2000/XP!
A: Check the drivers for the ATA controllers and/or SCSI host adapters. Specifically:
Q: Memory Bandwidth Benchmark (EMMX/SSE(2) version) crashes my OS with different errors!
A: Your memory timings are too aggressive; set the BIOS memory timings by SPD and turn off any Ultra or Turbo options. If you're using SDRAM set 3-3-3 timings; if DDR set 2.5-3-3 2CMD.
Q: Sandra 8.x BSODs with BAD_POOL_CALLER in Windows XP!
A: Make sure you're using Windows XP video drivers with proper OpenGL support; also update to Sandra 8.68 or later.
Q: Sandra 8.x crashes with missing OPENGL32.DLL on Windows 9X!
A: Please install OpenGL for Windows 9X or update your video driver to a version that has a OpenGL ICD included.
Q: Sandra 8.x crashes with missing ODBC32.DLL on Windows 9X!
A: You need to install MDAC w/ODBC support, at least version 3.50 or later (3.52 recommended).
Q: Sandra 7.5x/8.x crashes with missing WS_32.DLL on Windows 95!
A: Upgrade to Windows 98/Me or later or Install WinSock 2 support from Microsoft's site. Do note that Sandra 8.x require at least Windows 98.
Q: Sandra 2002 crashes in Mainboard Information with different errors!
A: Right-click module, select Options and uncheck Include Mainboard Info.
Q: Sandra crashes with an exception in MFC42.DLL!
A: See Install Problems.
Q: Sandra crashes with my SiS chipset!
A: There is a bug that affects the support for P5 SiS 530, 540 and P6 SiS 620, 630 chipsets. If you're using Sandra 7.5x please update to version 8.x or go back to an earlier version.
Q: The Modules Information module crashes.
A: This module does not work if you have a 2D Matrox video card installed (e.g. Millennium, Millennium II, Mystique) and the original drivers. First, verify that the drivers are the problem by changing to the Standard VGA Display Driver (640x480 16 colours). Both Windows 98 and DirectX 5/6 and later come with drivers for these video cards which should work. Make sure you download the complete version, not just the core.
Please note that it may not be possible to fix this problem with any Matrox drivers. However, you can try the latest Unified drivers from Matrox Website. Please let them know of this problem!
This module also does not work with drivers for the Neomagic 128/256 video adapters (usually found in laptop computers). Follow the same steps as outlined above, and check for new video drivers on the manufacturer's web site. Please let them know of this problem!
Q: Sandra crashes/locks on my Intel/Dell/Gateway mainboard/system!
A: Update to Sandra version 6.60 or later.
Q: Module Video Information corrupts the screen / lockup with nVidia XP display drivers!
A: This is an issue with the VESA VBE calls in Windows that seem to cause the driver to change state. To fix, right-click module and uncheck Include VESA BIOS Info.
Q: Module Video Information locks the computer / monitor powers down!
A: This is a bug in ATI's latest video drivers (e.g. 86114) for the Rage 128 series of cards. When querying the video BIOS through the VESA VBE interface the card locks and the monitor powers down. A hard reset is needed.
See Crash/Black screen with ATI Rage 128 article on ATI's knowledge base for more information and fix.
Q: Modules System Information, Mainboard Information, CPU & BIOS Information cause Fatal Exception 0D in Windows
A: Update to Sandra version 6.00 or later. Your Athlon system is not supported by the old version of Sandra you have.
Q: Modules System Information, Mainboard Information, CPU & BIOS Information crash.
Q: Module SAN16 crashes!
A: In module list (main window), right-click a module, choose Options and uncheck Include DMI Information. If it works, repeat for the other modules. Your BIOS does not support DMI properly in Windows. Find a newer BIOS version, and flash it. If no new version is available - contact your mainboard/system manufacturer. If you're running a version of Sandra earlier than 2.05, please upgrade to the latest version.
Q: Modules Mainboard Information and CPU & BIOS Information lock up!
A: Try the following: in module list (main window), right-click a module, choose Options and:
Q: DirectX module crashes with DirectX 6.0!
Q: DirectX module crashes with exception 10H
A: Upgrade to DirectX 6.1 or later. DirectX @ Microsoft. DirectX 6.0 does not work with multi-threaded applications like Sandra.
Q: DirectX module crashes with DirectX 1, 2 or 3 (including NT4 version)
A: Upgrade to Sandra version 4.10 or later.
Q: The CPU MultiMedia Benchmark (SSE/2 tests in fact) crashes on my system
A: Your operating system does not support the new SSE/2 processor state. If you're running Windows 95, upgrade to Windows 2000/XP. If you're running Windows NT, upgrade to SP6 or later.
Q: The CPU MultiMedia Benchmark module crashes on SMP box
A: If the processors have different model/stepping versions, make sure the boot processor is the one that has the lowest version. If the processors have different feature sets, make sure the BSP (boot processor) is the one with the lowest feature set. (e.g. in a PII & PIII SMP box, make the PII the BSP)
Q: Sandra crashes at start-up with a Trumpet WinSock
A: It seems there is an incompatibility between Sandra and Trumpet. It may be due to the use of the IE web-engine. There is no fix at this time - however the standard Microsoft WinSock (which you can upgrade to version 2.2) is very good.
Q: My non-Microsoft mouse locks!
A: Download the latest drivers from your mouse manufacturer. For example the newest Kesington Mouse/Trackball drivers fix this problem. If you have a graphics tablet, make sure it's configured properly and the drivers are also recent.
Q: The Printer Information module reports "Out of Memory"!
A: Right-click the module, select Options and uncheck Printer Modes Information. Upgrade to Sandra version 4.20 or later and install a printer if none are installed. Some Epson drivers cause this problem.
Q: The Printer Information module locks!
A: If you have networked printers which are off-line or their print servers are unavailable for some reason, the information gathering may take some time depending on the time-outs. Sometimes this can take 2-10 minutes depending on the number of printers. Therefore, the module does not actually lock - let it finish.
Q: The Network Information module locks!
A: On large networks with many workgroups and hosts this module may take some considerable time to scan them all (2-10 minutes). So the module does not actually lock but takes a long time to complete.
Q: The MCI Information module crashes.
A: Go to Control Panel - Multimedia - Advanced - Media Control Devices. Select LiveAudioMetafile and click Properties. Select Do not use this Media Control Device and click OK. Do the same for DBCRMVideo device. Alternatively, update to Sandra version 4.20 or later.